Update test to handle moving from microbatch environment variable to behavior flag #167
+3
−3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ranch of dbt-adapters
4 tasks
QMalcolm
force-pushed
the
qmalcolm--move-to-microbatch-behavior-flag
branch
from
583a46b
to
911fb19
Compare
|
Closing because this is no longer going to be merged, moving back to a POC Draft PR (#173) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
resolves #N/A
Problem
dbt-adapters and dbt-core are moving from using an environment variable for gating microbatch functionality to a behavior flag (dbt-labs/dbt-adapters#323, dbt-labs/dbt-core#10799). Additionally, dbt-adapters is adding more test stubs around this, and we wan to use those test stubs
Solution
Use the test stubs provided by dbt-adapters to test the switch from environment variable for gating microbatch functionality to a behavior flag.
Checklist